Skip to content

Conversation

@clydin
Copy link
Member

@clydin clydin commented Oct 13, 2025

This commit updates the version of vitest and its related packages from 3.2.4 to 4.0.0 within the unit testing system.

This major version update for Vitest introduces several changes that are addressed here:

  • The coverage.all option has been removed in Vitest v4. Accordingly, the coverageAll option has been removed from the unit-test builders schema and its usage has been removed from the Karma and Vitest test runner implementations.
  • The browser provider mechanism has been updated. Vitest now uses provider-specific packages (e.g., @vitest/browser-playwright) instead of the general @vitest/browser package. The browser configuration setup has been made asynchronous and now dynamically loads the appropriate provider.

@clydin clydin added the target: major This PR is targeted for the next major release label Oct 13, 2025
@angular-robot angular-robot bot added area: build & ci Related the build and CI infrastructure of the project area: @angular/build labels Oct 13, 2025
@clydin clydin force-pushed the unit-test/update-vitest-v4-beta branch 2 times, most recently from c298eee to 127adee Compare October 13, 2025 23:16
@clydin clydin force-pushed the unit-test/update-vitest-v4-beta branch 2 times, most recently from 3d6e145 to eb7b497 Compare October 22, 2025 15:24
@clydin clydin changed the title build(@angular/build): update vitest to v4.0.0-beta build(@angular/build): update vitest to v4.0.0 Oct 22, 2025
This commit updates the version of `vitest` and its related packages from `3.2.4` to `4.0.0` within the unit testing system.

This major version update for Vitest introduces several changes that are addressed here:
- The `coverage.all` option has been removed in Vitest v4. Accordingly, the `coverageAll` option has been removed from the unit-test builders schema and its usage has been removed from the Karma and Vitest test runner implementations.
- The browser provider mechanism has been updated. Vitest now uses provider-specific packages (e.g., @vitest/browser-playwright) instead of the general @vitest/browser package. The browser configuration setup has been made asynchronous and now dynamically loads the appropriate provider.
@clydin clydin force-pushed the unit-test/update-vitest-v4-beta branch from eb7b497 to 3b0702b Compare October 22, 2025 15:26
@clydin clydin added action: review The PR is still awaiting reviews from at least one requested reviewer and removed state: blocked on upstream labels Oct 22, 2025
@clydin clydin added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Oct 22, 2025
@clydin clydin merged commit 220961f into angular:main Oct 22, 2025
33 checks passed
@clydin clydin deleted the unit-test/update-vitest-v4-beta branch October 22, 2025 16:19
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Nov 22, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: @angular/build area: build & ci Related the build and CI infrastructure of the project target: major This PR is targeted for the next major release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants